ci: publish crates via crates.io Trusted Publishing, not a static token - #208
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
muscariello
force-pushed
the
ci/crates-io-trusted-publishing
branch
from
September 4, 2026 08:02
2365b09 to
01bd462
Compare
release-plz already exchanges a GitHub Actions OIDC token for a short-lived crates.io token whenever no CARGO_REGISTRY_TOKEN is set — no flag needed. All 13 published crates are registered as Trusted Publishers on crates.io for this repo + release-rust.yml, so the static secret and the step that checked for it can just go. agntcy/slim's release-rust.yaml, pinned to the same release-plz/action commit, already runs this way. Signed-off-by: Luca Muscariello <muscariello@ieee.org>
muscariello
force-pushed
the
ci/crates-io-trusted-publishing
branch
from
September 4, 2026 08:13
01bd462 to
9d7639f
Compare
msardara
approved these changes
Sep 4, 2026
muscariello
added a commit
that referenced
this pull request
Sep 4, 2026
#207 bumped the workspace to 0.1.7 and merged, but its publish run failed on the Trusted Publishing requirement #208 later fixed. With release_always = false nothing retried it: release skipped every later push, and release-pr would not bump past a version crates.io has not seen. Signed-off-by: Luca Muscariello <muscariello@ieee.org>
muscariello
added a commit
that referenced
this pull request
Sep 4, 2026
#207 bumped the workspace to 0.1.7 and merged, but its publish run failed on the Trusted Publishing requirement #208 later fixed. With release_always = false nothing retried it: release skipped every later push, and release-pr would not bump past a version crates.io has not seen. Signed-off-by: Luca Muscariello <muscariello@ieee.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
crates.io now requires Trusted Publishing for
agntcy-shadi-agent-transport-slim, which broke the last release. All 13 published crates are registered as Trusted Publishers now (repo owner confirmed).release-plz already does the OIDC exchange itself when no
CARGO_REGISTRY_TOKENis set — no new workflow logic needed, just delete the secret and the step that checked for it.agntcy/slimalready runs this way on the same release-plz version.Delete the
CARGO_REGISTRY_TOKENrepo secret once a real release confirms this works.